-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd-push-container-manifest: change image key schema #3129
Conversation
a84bfc7
to
1fdf599
Compare
So existing 4.12 |
1fdf599
to
9a958d8
Compare
Exactly, yes. So one alternatives is to add a separate definition temporarily with the looser requirement, and then merge them back in later. I can do that if we want, but it didn't seem worth the overhead. |
Let's hold this until we discuss #3122 (comment). |
9a958d8
to
c573a4b
Compare
c573a4b
to
9addd2c
Compare
Prow hitting
which looks like openshift/os#594, though that path doesn't look like a 9p mount. /retest |
In the RHCOS pipeline, we want to be able to tag the same image using both the stream name and the build ID.
The `oscontainer` and `base-oscontainer` keys should follow the same schema. Currently, the former has a `digest` field, while the other one does not. Tweak `cosa push-container-manifest` and `cosa push-container` so that they follows the new schema. (Though note the latter command will be deleted soon). To keep previous 4.12 `meta.json` files valid, this loosens the `image` schema definition so that `digest` is now optional. Once we branch for 4.12, we will undo this change so that it becomes required again. Fixes coreos#3122
9addd2c
to
7441106
Compare
Updated! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. A few more suggestions!
7441106
to
9fad3cb
Compare
As discussed in coreos#3122, ART needs the arch-specific digest in the `meta.json` rather than the manifest list digest. FCOS isn't planning to use the digest so doesn't care about which one gets chosen. Update `cosa push-container-manifest` to use the arch-specific digest.
9fad3cb
to
d40984d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/override ci/prow/rhcos It doesn't test this and it's taking too long. It passed on other derivative PRs that include almost exactly this code anyway. |
@jlebon: Overrode contexts on behalf of jlebon: ci/prow/rhcos In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The
oscontainer
andbase-oscontainer
keys should follow the sameschema. Currently, the former has a
digest
field, while the other onedoes not. Tweak
cosa push-container-manifest
andcosa push-container
so that they follows the new schema. (Though note the latter command
will be deleted soon).
To keep previous 4.12
meta.json
files valid, this loosens theimage
schema definition so that
digest
is now optional. Once we branch for4.12, we will undo this change so that it becomes required again.
Fixes #3122